home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Experimental BBS Explossion 3
/
Experimental BBS Explossion III.iso
/
gus
/
sdkdigv9.zip
/
SDKV9N36.TXT
< prev
next >
Wrap
Text File
|
1994-04-01
|
4KB
|
90 lines
Apparently-To: john.smith@gravis.com
GUS Programmer's Digest Thu, 31 Mar 94 17:38 PST Volume 9: Issue 36
Today's Topics:
GUS Programmer's Digest V9 #35
Samples crossing 256K boundaries ...
Standard Info:
- Meta-info about the GUS can be found at the end of the Digest.
- Before you ask a question, please READ THE FAQ.
----------------------------------------------------------------------
Date: Thu, 31 Mar 1994 10:50:33 -0500 (EST)
From: Phat H Tran <ptran@sciborg.uwaterloo.ca>
Subject: Re: GUS Programmer's Digest V9 #35
> Date: Wed, 30 Mar 1994 11:18:35 SAT
> From: "Michael Patricios" <PATRICIO@odie.ee.wits.ac.za>
> Subject: Why should enitire sample be in a 256K bank??
>
> OK, so I got my GUS. Great card. Then I wrote a MOD player for it. It
> was a MUCH easier to do than with my old SB pro! OK fine. Then I read
> in the SDK dox that a sample has to be totally in a 256K bank of
> memory, ie: it should not cross the boundary. BUT!!!!!!! I tried
> uploading samples to GUS DRAM in all sorts of positions, crossing
> 256K boundaries etc.. The samples played fine, sample looping worked
> fine (it just occured to me that I forgot to test volume ramping, but
> I bet it will probably be fine too). What was the reason then for this
> restriction (256K boundary) which is stated explicitly in the SDK
> several times, but NO reasons given for it????
I assume that you tried all that using just 8-bit MOD samples. The
256kB boundaries really only matter with 16-bit samples, I've
been told.
Phat.
------------------------------
Date: Thu, 31 Mar 94 07:23:30 EST
From: support@fortech.com (Technical Support)
Subject: Samples crossing 256K boundaries ...
> From: "Michael Patricios" <PATRICIO@odie.ee.wits.ac.za>
> Subject: Why should enitire sample be in a 256K bank??
> I bet it will probably be fine too). What was the reason then for this
> restriction (256K boundary) which is stated explicitly in the SDK
> several times, but NO reasons given for it????
> Anyone?
An 8 bit sample can be played across a 256K boundary without a problem.
A 16 bit sample cannot. If you know your app will be only dealing with
8 bit data, then you can remove this restriction. Some minor mods
to the memory allocation routines will allow you whole memory space
to be treated as one pool rather than multiple 256K pools.
Forte.
------------------------------
End of GUS Programmer's Digest V9 #36
*************************************
To post to tomorrow's digest: <gus-sdk@mail.orst.edu>
To (un)subscribe or get help: <gus-sdk-request@mail.orst.edu>
To contact a human (last resort): <gus-sdk-owner@mail.orst.edu>
FTP Sites Archive Directories
--------- ------- -----------
Main N.American Site: archive.orst.edu pub/packages/gravis
wuarchive.wustl.edu systems/ibmpc/ultrasound
Main Asian Site: nctuccca.edu.tw PC/ultrasound
European Callers ONLY: theoris.rz.uni-konstanz.de pub/sound/gus
Submissions: archive.epas.utoronto.ca pub/pc/ultrasound/submit
Newly Validated Files: archive.epas.utoronto.ca pub/pc/ultrasound
Mirrors: garbo.uwasa.fi mirror/ultrasound
MailServer For Archive Access: Email to <mail-server@nike.rz.uni-konstanz.de>
Hints:
- Get the FAQ from the FTP sites or the request server.
- Mail to <gus-sdk-request@mail.orst.edu> for info about other GUS
related mailing lists (general use, musician's, etc.).